Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b49f96e1eb0571116a5ee3cb7d7e6615d35425b74fee2d2f22a15a93a7449d25

Tx prefix hash: 6fe1862dfa45e7bb5b6f1ba465ef92002c64a66c51a59975926529deb6f765d4
Tx public key: 252617df8ed5d1e1326027381193c14ddfdad2bc0c1df0f80cf2241e48895a1f
Timestamp: 1715090354 Timestamp [UCT]: 2024-05-07 13:59:14 Age [y:d:h:m:s]: 00:339:04:58:25
Block: 1016860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242466 RingCT/type: yes/0
Extra: 01252617df8ed5d1e1326027381193c14ddfdad2bc0c1df0f80cf2241e48895a1f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe8af4dd7a9d18a29d9ebae9df3c23e22c865c02099b73485978538200ad68a8 0.600000000000 1480569 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": 1016870, "vin": [ { "gen": { "height": 1016860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe8af4dd7a9d18a29d9ebae9df3c23e22c865c02099b73485978538200ad68a8" } } ], "extra": [ 1, 37, 38, 23, 223, 142, 213, 209, 225, 50, 96, 39, 56, 17, 147, 193, 77, 223, 218, 210, 188, 12, 29, 240, 248, 12, 242, 36, 30, 72, 137, 90, 31, 2, 17, 0, 0, 0, 3, 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