Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c2c7cab95553d1204393b275481ebd277ae8e1d323ad03664507dbbe045bc13

Tx prefix hash: e26327fb27515261762d68dd2df671b4ecfe44a4d3640c30fa092c62b52ac6a2
Tx public key: 154255ac80d46bed46f8adcff5c6d7db4c559fb6a695bf5fbcf6eee95ae160c7
Timestamp: 1580587941 Timestamp [UCT]: 2020-02-01 20:12:21 Age [y:d:h:m:s]: 04:291:03:11:24
Block: 56748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1099263 RingCT/type: yes/0
Extra: 01154255ac80d46bed46f8adcff5c6d7db4c559fb6a695bf5fbcf6eee95ae160c70211000000168a2ee0d9000000000000000000

1 output(s) for total of 398.080717897000 dcy

stealth address amount amount idx
00: 8fb238307f21520fefd12df6eab0dc7e7d04e1b460d040aa783763e38d07a2cc 398.080717897000 104627 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": 56758, "vin": [ { "gen": { "height": 56748 } } ], "vout": [ { "amount": 398080717897, "target": { "key": "8fb238307f21520fefd12df6eab0dc7e7d04e1b460d040aa783763e38d07a2cc" } } ], "extra": [ 1, 21, 66, 85, 172, 128, 212, 107, 237, 70, 248, 173, 207, 245, 198, 215, 219, 76, 85, 159, 182, 166, 149, 191, 95, 188, 246, 238, 233, 90, 225, 96, 199, 2, 17, 0, 0, 0, 22, 138, 46, 224, 217, 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