Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43f78c94cf1208da99369ee21a7abebb915e15fea9261100043bef71889f59fa

Tx prefix hash: 44cfb6ff4738a7dfabf5e9ff794ee46e0ca23ade502358e31123f0bec71db72b
Tx public key: ff970f2915cd36874ae85baf69b08c6827d0df8bc41904eea3acfb36c18b77cc
Timestamp: 1578411000 Timestamp [UCT]: 2020-01-07 15:30:00 Age [y:d:h:m:s]: 05:057:08:30:59
Block: 40615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1190968 RingCT/type: yes/0
Extra: 01ff970f2915cd36874ae85baf69b08c6827d0df8bc41904eea3acfb36c18b77cc0211000000dcbd0f9f9f000000000000000000

1 output(s) for total of 450.231520642000 dcy

stealth address amount amount idx
00: 12761ed0a35e02e2ee8660e8ac1d23aea9af1921e6158d5d29bf4e1fdf500b98 450.231520642000 71470 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": 40625, "vin": [ { "gen": { "height": 40615 } } ], "vout": [ { "amount": 450231520642, "target": { "key": "12761ed0a35e02e2ee8660e8ac1d23aea9af1921e6158d5d29bf4e1fdf500b98" } } ], "extra": [ 1, 255, 151, 15, 41, 21, 205, 54, 135, 74, 232, 91, 175, 105, 176, 140, 104, 39, 208, 223, 139, 196, 25, 4, 238, 163, 172, 251, 54, 193, 139, 119, 204, 2, 17, 0, 0, 0, 220, 189, 15, 159, 159, 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