Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 310ead83a7178effae062c7b82da3cc47bdc3f1eefc9b92d5e2cb816b1888866

Tx prefix hash: 71f612df13831e68f33dc98c3780223f66ba397aeb40d234f13e7592d37071d4
Tx public key: a7f1d8c57a075d8c90f94667925dd5e3af461a8863ff9a237f0e43a18724dc26
Timestamp: 1661385832 Timestamp [UCT]: 2022-08-25 00:03:52 Age [y:d:h:m:s]: 03:072:08:49:51
Block: 573135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 831545 RingCT/type: yes/0
Extra: 01a7f1d8c57a075d8c90f94667925dd5e3af461a8863ff9a237f0e43a18724dc2602110000000275e3f0e9000000000000000000

1 output(s) for total of 7.744010332000 dcy

stealth address amount amount idx
00: 5e2abf43f4c41856af9cbc908910ee193c0552c0ea14daca556f67f34b9d2d73 7.744010332000 1006411 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": 573145, "vin": [ { "gen": { "height": 573135 } } ], "vout": [ { "amount": 7744010332, "target": { "key": "5e2abf43f4c41856af9cbc908910ee193c0552c0ea14daca556f67f34b9d2d73" } } ], "extra": [ 1, 167, 241, 216, 197, 122, 7, 93, 140, 144, 249, 70, 103, 146, 93, 213, 227, 175, 70, 26, 136, 99, 255, 154, 35, 127, 14, 67, 161, 135, 36, 220, 38, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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