Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1375f7cc49a178e898473c77d4e1a2d58b8d604ce7f18d146e0a66efa92bfa58

Tx prefix hash: 32f3711181706c5df3a6213049601657f9a40851f52009d93321cd92a12d14c4
Tx public key: 23929458d3613b4c97088ba5e836430807a6bd50b49a3c6b0c83ece662dc9395
Timestamp: 1699744575 Timestamp [UCT]: 2023-11-11 23:16:15 Age [y:d:h:m:s]: 01:071:14:39:53
Block: 889630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312544 RingCT/type: yes/0
Extra: 0123929458d3613b4c97088ba5e836430807a6bd50b49a3c6b0c83ece662dc93950211000000034b8f5122000000000000000000

1 output(s) for total of 0.692287525000 dcy

stealth address amount amount idx
00: 834b283ac0e16ad0ce3f2975f572ba526493af14ad16b39e954c1c07b6d086e8 0.692287525000 1345637 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 889640, "vin": [ { "gen": { "height": 889630 } } ], "vout": [ { "amount": 692287525, "target": { "key": "834b283ac0e16ad0ce3f2975f572ba526493af14ad16b39e954c1c07b6d086e8" } } ], "extra": [ 1, 35, 146, 148, 88, 211, 97, 59, 76, 151, 8, 139, 165, 232, 54, 67, 8, 7, 166, 189, 80, 180, 154, 60, 107, 12, 131, 236, 230, 98, 220, 147, 149, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8