Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df46f47cc74489cccfdb5cfe3cf3a37bc50a567670dd397431d9291b8c9404af

Tx prefix hash: 5e6ac758c820bdaf6f6a48d2be947b2f49e32cbda077d50277685e29904a6718
Tx public key: 6d4edc3d2abbd6a6fe2a1ecc4a1f18018da44f040c2cac1b9d0cc1cb1b01d4c5
Timestamp: 1734901927 Timestamp [UCT]: 2024-12-22 21:12:07 Age [y:d:h:m:s]: 00:102:14:33:16
Block: 1181013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73085 RingCT/type: yes/0
Extra: 016d4edc3d2abbd6a6fe2a1ecc4a1f18018da44f040c2cac1b9d0cc1cb1b01d4c502110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bff7866818521b4c1d7ad94f5e1d54957a64b81ab68e4a40f589592bbcbdfee0 0.600000000000 1667428 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": 1181023, "vin": [ { "gen": { "height": 1181013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bff7866818521b4c1d7ad94f5e1d54957a64b81ab68e4a40f589592bbcbdfee0" } } ], "extra": [ 1, 109, 78, 220, 61, 42, 187, 214, 166, 254, 42, 30, 204, 74, 31, 24, 1, 141, 164, 79, 4, 12, 44, 172, 27, 157, 12, 193, 203, 27, 1, 212, 197, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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