Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70fc4d31447614859ed250452f3a8b29af79b4e9a229208ee403af7fbaf53aff

Tx prefix hash: 1edb6a05bf1c227f6f97dca8990d386817964e7b76ecc50f443e3cf84b78dbb3
Tx public key: dd1be8d57c6cfccf0e5c356c76bb08734a3238d094442e1d1190f19951501898
Timestamp: 1647398469 Timestamp [UCT]: 2022-03-16 02:41:09 Age [y:d:h:m:s]: 02:282:21:33:40
Block: 459379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 721724 RingCT/type: yes/0
Extra: 01dd1be8d57c6cfccf0e5c356c76bb08734a3238d094442e1d1190f1995150189802110000000f5eb576c5000000000000000000

1 output(s) for total of 18.445351714000 dcy

stealth address amount amount idx
00: 92b9956892f43cc1dd717cbd1c9fb8067a5c3744600c25204b029c2a2f66cec3 18.445351714000 876102 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": 459389, "vin": [ { "gen": { "height": 459379 } } ], "vout": [ { "amount": 18445351714, "target": { "key": "92b9956892f43cc1dd717cbd1c9fb8067a5c3744600c25204b029c2a2f66cec3" } } ], "extra": [ 1, 221, 27, 232, 213, 124, 108, 252, 207, 14, 92, 53, 108, 118, 187, 8, 115, 74, 50, 56, 208, 148, 68, 46, 29, 17, 144, 241, 153, 81, 80, 24, 152, 2, 17, 0, 0, 0, 15, 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