Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37e921551c414ecf6bb64b13d3c39fd7f29078afa422b7131a61714e19f79eb0

Tx prefix hash: 8c7d05c27accc3888f602aef232f40521a1001e7375fbafecee0c19b2730e221
Tx public key: 1b78210ac685a4da79ba0aa3745c25457a480f282479e25a6d1d40c023a82fb1
Timestamp: 1722612291 Timestamp [UCT]: 2024-08-02 15:24:51 Age [y:d:h:m:s]: 01:096:01:20:15
Block: 1079214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327115 RingCT/type: yes/0
Extra: 011b78210ac685a4da79ba0aa3745c25457a480f282479e25a6d1d40c023a82fb102110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c804b05534d9914af8e3d3022638be8f93fa87d30d5115e1d2b31760c8fb798 0.600000000000 1552069 of 15

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": 1079224, "vin": [ { "gen": { "height": 1079214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c804b05534d9914af8e3d3022638be8f93fa87d30d5115e1d2b31760c8fb798" } } ], "extra": [ 1, 27, 120, 33, 10, 198, 133, 164, 218, 121, 186, 10, 163, 116, 92, 37, 69, 122, 72, 15, 40, 36, 121, 226, 90, 109, 29, 64, 192, 35, 168, 47, 177, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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