Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 426c34cf988b7b2322a4678cba5948eb96baf28fc2edfca76554aa6eb79d2901

Tx prefix hash: 61f4b4de08c73a862be1d95d9b30ec020e7ab1ab5f93d0d107ce3a795ca46d21
Tx public key: bfc4f400b9acf1846180f8bbde542babb28cc491bc8e8d876e01226abff32a8a
Timestamp: 1634807401 Timestamp [UCT]: 2021-10-21 09:10:01 Age [y:d:h:m:s]: 03:079:07:00:35
Block: 357349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 834925 RingCT/type: yes/0
Extra: 01bfc4f400b9acf1846180f8bbde542babb28cc491bc8e8d876e01226abff32a8a02110000000b7e786c8c000000000000000000

1 output(s) for total of 40.174902662000 dcy

stealth address amount amount idx
00: cbd3eec59cd61d598059d4e21b1ac8461369ae14b9a129cee2f0864869e266eb 40.174902662000 728707 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": 357359, "vin": [ { "gen": { "height": 357349 } } ], "vout": [ { "amount": 40174902662, "target": { "key": "cbd3eec59cd61d598059d4e21b1ac8461369ae14b9a129cee2f0864869e266eb" } } ], "extra": [ 1, 191, 196, 244, 0, 185, 172, 241, 132, 97, 128, 248, 187, 222, 84, 43, 171, 178, 140, 196, 145, 188, 142, 141, 135, 110, 1, 34, 106, 191, 243, 42, 138, 2, 17, 0, 0, 0, 11, 126, 120, 108, 140, 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