Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfffa4e160c7f1c18d52c71379e25475b4c9d7c0c615143b745ba2b4cd02aa5f

Tx prefix hash: 3b3e07e9c17da76b9a4651181ab741ec5bc98a9102573aa7528095395990d435
Tx public key: 67531316580e635b4137ce183824a180278e2dee1870edeffbb896fcc3fd058a
Timestamp: 1697715360 Timestamp [UCT]: 2023-10-19 11:36:00 Age [y:d:h:m:s]: 01:096:16:17:31
Block: 873008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330305 RingCT/type: yes/0
Extra: 0167531316580e635b4137ce183824a180278e2dee1870edeffbb896fcc3fd058a02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.785890640000 dcy

stealth address amount amount idx
00: a3a39a803d4fce54f4eea1e6904f0180e4f66a6da3f623989b0d69b0fc313927 0.785890640000 1328120 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": 873018, "vin": [ { "gen": { "height": 873008 } } ], "vout": [ { "amount": 785890640, "target": { "key": "a3a39a803d4fce54f4eea1e6904f0180e4f66a6da3f623989b0d69b0fc313927" } } ], "extra": [ 1, 103, 83, 19, 22, 88, 14, 99, 91, 65, 55, 206, 24, 56, 36, 161, 128, 39, 142, 45, 238, 24, 112, 237, 239, 251, 184, 150, 252, 195, 253, 5, 138, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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