Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 770101cfdd54ba8488808945e82f2bb626382dfd07e3bfc9019adf1988d70dc0

Tx prefix hash: e4b98f20700402fdfb446a6750905acfca0ed0a7cee6c6dc34582c67c0f9d05f
Tx public key: c8212d9b2a53db8eccc6dd565a7f723c67339c0988d67ec4a92bdf6e4117682e
Timestamp: 1719627172 Timestamp [UCT]: 2024-06-29 02:12:52 Age [y:d:h:m:s]: 01:132:11:50:33
Block: 1054466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353228 RingCT/type: yes/0
Extra: 01c8212d9b2a53db8eccc6dd565a7f723c67339c0988d67ec4a92bdf6e4117682e0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66d7536cddfcc52549ac0ed4359fa39c5ee40c917ebc9e93602901848e9cc7c7 0.600000000000 1524827 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": 1054476, "vin": [ { "gen": { "height": 1054466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66d7536cddfcc52549ac0ed4359fa39c5ee40c917ebc9e93602901848e9cc7c7" } } ], "extra": [ 1, 200, 33, 45, 155, 42, 83, 219, 142, 204, 198, 221, 86, 90, 127, 114, 60, 103, 51, 156, 9, 136, 214, 126, 196, 169, 43, 223, 110, 65, 23, 104, 46, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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