Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 515cc79f4c99942d803e5695ab6be6b808877ba0705e28489e3a6b5a78ae9646

Tx prefix hash: e211b7876642ceb0a6cbce359d4923cdce88194b5276110675770e938961f324
Tx public key: 71a467c0e1f59cc4418db99bce1894fc204b8bf9f29d2f8c2c35e24ab07bca83
Timestamp: 1633218283 Timestamp [UCT]: 2021-10-02 23:44:43 Age [y:d:h:m:s]: 04:033:10:45:11
Block: 345467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1059258 RingCT/type: yes/0
Extra: 0171a467c0e1f59cc4418db99bce1894fc204b8bf9f29d2f8c2c35e24ab07bca83021100000012f29d7abf000000000000000000

1 output(s) for total of 43.989021164000 dcy

stealth address amount amount idx
00: 0703cc845560a9b31e351f8d0b4f28c14ca1516434f3107a60d140226fb8f48b 43.989021164000 708665 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": 345477, "vin": [ { "gen": { "height": 345467 } } ], "vout": [ { "amount": 43989021164, "target": { "key": "0703cc845560a9b31e351f8d0b4f28c14ca1516434f3107a60d140226fb8f48b" } } ], "extra": [ 1, 113, 164, 103, 192, 225, 245, 156, 196, 65, 141, 185, 155, 206, 24, 148, 252, 32, 75, 139, 249, 242, 157, 47, 140, 44, 53, 226, 74, 176, 123, 202, 131, 2, 17, 0, 0, 0, 18, 242, 157, 122, 191, 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