Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bf8864417f7b295e3955937a04c27c6085b18aa9116ad1549074e6c85029e88

Tx prefix hash: 019fd658c35e089795ff7bc6053e91686f956907cb4ab6816015c16176df8e76
Tx public key: 0bfb16e9eb792faeb3da4ca9a0452dc7f916dde01b1dcec25e6cb4e24b2a9533
Timestamp: 1588144271 Timestamp [UCT]: 2020-04-29 07:11:11 Age [y:d:h:m:s]: 04:244:06:56:13
Block: 96942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1088110 RingCT/type: yes/0
Extra: 010bfb16e9eb792faeb3da4ca9a0452dc7f916dde01b1dcec25e6cb4e24b2a953302110000000960e3cc90000000000000000000

1 output(s) for total of 292.953829303000 dcy

stealth address amount amount idx
00: 18ffcad44aca75d0d34de1f3843dff711d8660c144e638e504dee163247d3865 292.953829303000 171865 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": 96952, "vin": [ { "gen": { "height": 96942 } } ], "vout": [ { "amount": 292953829303, "target": { "key": "18ffcad44aca75d0d34de1f3843dff711d8660c144e638e504dee163247d3865" } } ], "extra": [ 1, 11, 251, 22, 233, 235, 121, 47, 174, 179, 218, 76, 169, 160, 69, 45, 199, 249, 22, 221, 224, 27, 29, 206, 194, 94, 108, 180, 226, 75, 42, 149, 51, 2, 17, 0, 0, 0, 9, 96, 227, 204, 144, 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