Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41f7725a7bc0befff0fd0ba860030a7c9d5e7392bb82f0d59f2b8c5c2402218f

Tx prefix hash: e1eba700b9d05bb67fd83029c3b3cf4b164c56dc9189ad05e6c51d1d8cb87e77
Tx public key: e5d56d409832e266a6961dfc39ef76423e0c68cd8817f1e84f2f11b317a9b989
Timestamp: 1648693934 Timestamp [UCT]: 2022-03-31 02:32:14 Age [y:d:h:m:s]: 03:215:21:22:04
Block: 469990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 932279 RingCT/type: yes/0
Extra: 01e5d56d409832e266a6961dfc39ef76423e0c68cd8817f1e84f2f11b317a9b9890211000000025eb576c5000000000000000000

1 output(s) for total of 17.012828613000 dcy

stealth address amount amount idx
00: f10463ddb12dbbf898ea44ce32196ac360065c25f1c0fd7feca602092e353473 17.012828613000 889048 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": 470000, "vin": [ { "gen": { "height": 469990 } } ], "vout": [ { "amount": 17012828613, "target": { "key": "f10463ddb12dbbf898ea44ce32196ac360065c25f1c0fd7feca602092e353473" } } ], "extra": [ 1, 229, 213, 109, 64, 152, 50, 226, 102, 166, 150, 29, 252, 57, 239, 118, 66, 62, 12, 104, 205, 136, 23, 241, 232, 79, 47, 17, 179, 23, 169, 185, 137, 2, 17, 0, 0, 0, 2, 94, 181, 118, 197, 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