Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2da26447c21bcddf3c740c21d4b6d98c71fbea41fe23ee951144f90ac7be8d01

Tx prefix hash: e5caa195acafc7dd02635c0126d52400c01a618e6aa8e4dc15d5b3fb8e43a1d7
Tx public key: e804514fa72be677f2a5a4b04d845e863aaa91d5f3d15dd973f90d71f7887db6
Timestamp: 1706479925 Timestamp [UCT]: 2024-01-28 22:12:05 Age [y:d:h:m:s]: 01:103:14:25:20
Block: 945443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335155 RingCT/type: yes/0
Extra: 01e804514fa72be677f2a5a4b04d845e863aaa91d5f3d15dd973f90d71f7887db60211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd0f843eac425d60856201b86d31af5f7f5976b1e37df6e1e238213752e0ba84 0.600000000000 1403757 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": 945453, "vin": [ { "gen": { "height": 945443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd0f843eac425d60856201b86d31af5f7f5976b1e37df6e1e238213752e0ba84" } } ], "extra": [ 1, 232, 4, 81, 79, 167, 43, 230, 119, 242, 165, 164, 176, 77, 132, 94, 134, 58, 170, 145, 213, 243, 209, 93, 217, 115, 249, 13, 113, 247, 136, 125, 182, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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