Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab32c6d3e439169bea84d15fe6526a78e1b0dfa47e053650f82993a38203bbca

Tx prefix hash: 797822d74a48a4de693c87ba5376b94948907490e5edec153cd13503814ec78f
Tx public key: 6a0f6cd5f6618f9729ef0c916f17e3ee6d85d5c7bfde54218ba5d9917009325a
Timestamp: 1716769745 Timestamp [UCT]: 2024-05-27 00:29:05 Age [y:d:h:m:s]: 00:316:22:39:20
Block: 1030783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226509 RingCT/type: yes/0
Extra: 016a0f6cd5f6618f9729ef0c916f17e3ee6d85d5c7bfde54218ba5d9917009325a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6c563fd8b33db4e5ccd5013e9ec9854342890f263ae5adab1a0e8dde472798e 0.600000000000 1499072 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": 1030793, "vin": [ { "gen": { "height": 1030783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6c563fd8b33db4e5ccd5013e9ec9854342890f263ae5adab1a0e8dde472798e" } } ], "extra": [ 1, 106, 15, 108, 213, 246, 97, 143, 151, 41, 239, 12, 145, 111, 23, 227, 238, 109, 133, 213, 199, 191, 222, 84, 33, 139, 165, 217, 145, 112, 9, 50, 90, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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