Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 407723c8322634b18cbeb8eb9dd6013d09453dfc7ec17f52921564f588f469e4

Tx prefix hash: 4ed8fb1d98b64baf3bb5b5a79d7592946f8a85a404f2afceb755558a95d35280
Tx public key: 365c691acb9c6e60f13dcc0bfac2d8006fbdff744979e9c2b7798fb2343a625f
Timestamp: 1650376144 Timestamp [UCT]: 2022-04-19 13:49:04 Age [y:d:h:m:s]: 02:300:12:32:32
Block: 483607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 734465 RingCT/type: yes/0
Extra: 01365c691acb9c6e60f13dcc0bfac2d8006fbdff744979e9c2b7798fb2343a625f02110000000133af99f4000000000000000000

1 output(s) for total of 15.332376801000 dcy

stealth address amount amount idx
00: 323e139607ae12cb634bb3e5d0477070b4596d7389a9ec96fc5f59bbb4451422 15.332376801000 905318 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": 483617, "vin": [ { "gen": { "height": 483607 } } ], "vout": [ { "amount": 15332376801, "target": { "key": "323e139607ae12cb634bb3e5d0477070b4596d7389a9ec96fc5f59bbb4451422" } } ], "extra": [ 1, 54, 92, 105, 26, 203, 156, 110, 96, 241, 61, 204, 11, 250, 194, 216, 0, 111, 189, 255, 116, 73, 121, 233, 194, 183, 121, 143, 178, 52, 58, 98, 95, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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