Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 469e37dd14f66a0e019a36912db37f0c03672d3aa12cb8592307e43627cbdb50

Tx prefix hash: c076b1668b178daa7fcb0bcbb75b5a7941b3238ed2ecb627c3b04df4560c3aa5
Tx public key: 8f786768c81e6f5bc4a83b59088d3d3770f7f3d3fd0c780e15fe065fd36fb384
Timestamp: 1608256709 Timestamp [UCT]: 2020-12-18 01:58:29 Age [y:d:h:m:s]: 04:121:05:52:31
Block: 164240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1099040 RingCT/type: yes/0
Extra: 018f786768c81e6f5bc4a83b59088d3d3770f7f3d3fd0c780e15fe065fd36fb38402110000000990ce5c0f000000000000000000

1 output(s) for total of 175.315529266000 dcy

stealth address amount amount idx
00: 125ad506b9d4241651fa5683a3a27be78786aa8443a9e73eb0e05f162b436986 175.315529266000 296633 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": 164250, "vin": [ { "gen": { "height": 164240 } } ], "vout": [ { "amount": 175315529266, "target": { "key": "125ad506b9d4241651fa5683a3a27be78786aa8443a9e73eb0e05f162b436986" } } ], "extra": [ 1, 143, 120, 103, 104, 200, 30, 111, 91, 196, 168, 59, 89, 8, 141, 61, 55, 112, 247, 243, 211, 253, 12, 120, 14, 21, 254, 6, 95, 211, 111, 179, 132, 2, 17, 0, 0, 0, 9, 144, 206, 92, 15, 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