Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4282142f355410fb840c6ad82204f7971d696dc268190d6524ca9ee150780bf7

Tx prefix hash: 80c5478cecc5ec09256aeedc72e58f194cca76f550096e03e9533a458e4abbd8
Tx public key: bb46e0256bbed9155fd4e3cb6c18d822ca18c3e5766501ae1be02f3e3949fbe7
Timestamp: 1742441644 Timestamp [UCT]: 2025-03-20 03:34:04 Age [y:d:h:m:s]: 00:240:22:54:06
Block: 1243151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169928 RingCT/type: yes/0
Extra: 01bb46e0256bbed9155fd4e3cb6c18d822ca18c3e5766501ae1be02f3e3949fbe7021100000004bfa77623000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 870adc5b9e02df32bbb75d1e948a1ae7fbd877c3645c9da637428871a3060e07 0.600000000000 1730136 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": 1243161, "vin": [ { "gen": { "height": 1243151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "870adc5b9e02df32bbb75d1e948a1ae7fbd877c3645c9da637428871a3060e07" } } ], "extra": [ 1, 187, 70, 224, 37, 107, 190, 217, 21, 95, 212, 227, 203, 108, 24, 216, 34, 202, 24, 195, 229, 118, 101, 1, 174, 27, 224, 47, 62, 57, 73, 251, 231, 2, 17, 0, 0, 0, 4, 191, 167, 118, 35, 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