Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce74e439385d57615745cece6e6df591b1d1e0e69f09bcf64d88602338c62008

Tx prefix hash: 11c1b2e6f6fd42f2b3caba7cd79b01e889368be8f400641e9992db0470038673
Tx public key: 7deb6cd77d0ef260a1c490b035e355f1bb72f6e85bffd2666e44ea11e2c2ed0b
Timestamp: 1708998806 Timestamp [UCT]: 2024-02-27 01:53:26 Age [y:d:h:m:s]: 01:016:23:06:30
Block: 966361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273139 RingCT/type: yes/0
Extra: 017deb6cd77d0ef260a1c490b035e355f1bb72f6e85bffd2666e44ea11e2c2ed0b0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa378b9c7b9056650eefa22626cde9108c0ec1dea7619d0aba17301e969daa82 0.600000000000 1426118 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": 966371, "vin": [ { "gen": { "height": 966361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa378b9c7b9056650eefa22626cde9108c0ec1dea7619d0aba17301e969daa82" } } ], "extra": [ 1, 125, 235, 108, 215, 125, 14, 242, 96, 161, 196, 144, 176, 53, 227, 85, 241, 187, 114, 246, 232, 91, 255, 210, 102, 110, 68, 234, 17, 226, 194, 237, 11, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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