Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e990d86e5d6dc9a259bc53c1e3ea6d7f3d2fca3ac1d278ec5eb09708f7f63325

Tx prefix hash: 80776a6b1d0e7d74003e23419a091055e461940633bb5bb01038f331ec1122e8
Tx public key: f870b185e89b41b4fe0770ed5a8e0a58b1f9ce5475c688ac7909d091f32964f1
Timestamp: 1734168823 Timestamp [UCT]: 2024-12-14 09:33:43 Age [y:d:h:m:s]: 00:104:15:42:41
Block: 1174927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74573 RingCT/type: yes/0
Extra: 01f870b185e89b41b4fe0770ed5a8e0a58b1f9ce5475c688ac7909d091f32964f10211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 720992aa3889c8648d8ddb21a263cd709111e8ee50b5423c768daca6ce37d63d 0.600000000000 1661140 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": 1174937, "vin": [ { "gen": { "height": 1174927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "720992aa3889c8648d8ddb21a263cd709111e8ee50b5423c768daca6ce37d63d" } } ], "extra": [ 1, 248, 112, 177, 133, 232, 155, 65, 180, 254, 7, 112, 237, 90, 142, 10, 88, 177, 249, 206, 84, 117, 198, 136, 172, 121, 9, 208, 145, 243, 41, 100, 241, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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