Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9498919e3451a067286a699a9027835e7c849a30c2985a7fa6cfc428312925f8

Tx prefix hash: 2343b7467dbba19b0a57cdd78638116a966384fe97938f8e0e839453dee0b733
Tx public key: 8d9fd70e49e728cef69e6bb1a7de0f46ecb6af1671c02e9736dec8b250cf561c
Timestamp: 1724618623 Timestamp [UCT]: 2024-08-25 20:43:43 Age [y:d:h:m:s]: 01:074:09:02:13
Block: 1095850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311596 RingCT/type: yes/0
Extra: 018d9fd70e49e728cef69e6bb1a7de0f46ecb6af1671c02e9736dec8b250cf561c02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0edee7bd95d6dfb8cd4d2fea2be9a35bc043473cbed90a9ec60ffdf8f0e4de1 0.600000000000 1571033 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": 1095860, "vin": [ { "gen": { "height": 1095850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0edee7bd95d6dfb8cd4d2fea2be9a35bc043473cbed90a9ec60ffdf8f0e4de1" } } ], "extra": [ 1, 141, 159, 215, 14, 73, 231, 40, 206, 246, 158, 107, 177, 167, 222, 15, 70, 236, 182, 175, 22, 113, 192, 46, 151, 54, 222, 200, 178, 80, 207, 86, 28, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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