Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8355af6b6e2d3396fb17c0b7c7333b858716c0740b2d1f3248f44286bc8c55d0

Tx prefix hash: 19e38585c46c4711e2ccae7525c043d81c3e75c2a65a01c3c81e59f8690fa8f0
Tx public key: 078d64a00927229d24c68f2edafd765752c7aadb7faf20cb8f040b6b7b0f9fc3
Timestamp: 1734621486 Timestamp [UCT]: 2024-12-19 15:18:06 Age [y:d:h:m:s]: 00:108:11:08:56
Block: 1178690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77262 RingCT/type: yes/0
Extra: 01078d64a00927229d24c68f2edafd765752c7aadb7faf20cb8f040b6b7b0f9fc3021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b31e56785672cd1b72855e8346bf289a4ad3de3c0e4eec52cfac2121dc87dbb 0.600000000000 1665079 of 15

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": 1178700, "vin": [ { "gen": { "height": 1178690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b31e56785672cd1b72855e8346bf289a4ad3de3c0e4eec52cfac2121dc87dbb" } } ], "extra": [ 1, 7, 141, 100, 160, 9, 39, 34, 157, 36, 198, 143, 46, 218, 253, 118, 87, 82, 199, 170, 219, 127, 175, 32, 203, 143, 4, 11, 107, 123, 15, 159, 195, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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