Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e591ab291c8b91cd0f13518e24119527498c1468d95c985b3c90ec8fd5c8b7fb

Tx prefix hash: 49ab32a9b57d642e30df090aa2397a606ebbf5b455dda400ec833e6387942f3d
Tx public key: 27994b9468eef504115909d77935e8070b310784132445aa3bfb075cbf890d9e
Timestamp: 1578550748 Timestamp [UCT]: 2020-01-09 06:19:08 Age [y:d:h:m:s]: 05:056:06:47:55
Block: 41813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1190161 RingCT/type: yes/0
Extra: 0127994b9468eef504115909d77935e8070b310784132445aa3bfb075cbf890d9e021105c00b0300000000000000000000000000

1 output(s) for total of 446.125470078000 dcy

stealth address amount amount idx
00: a868b3e9a24bb8a48541b357f78d11c274767f8fb4dfc785a1ab57e00b56a4e0 446.125470078000 74905 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": 41823, "vin": [ { "gen": { "height": 41813 } } ], "vout": [ { "amount": 446125470078, "target": { "key": "a868b3e9a24bb8a48541b357f78d11c274767f8fb4dfc785a1ab57e00b56a4e0" } } ], "extra": [ 1, 39, 153, 75, 148, 104, 238, 245, 4, 17, 89, 9, 215, 121, 53, 232, 7, 11, 49, 7, 132, 19, 36, 69, 170, 59, 251, 7, 92, 191, 137, 13, 158, 2, 17, 5, 192, 11, 3, 0, 0, 0, 0, 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