Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f719a8356b544cfc769a6948ba33d3606142f0f1bba667d9303fa149e5e9abf

Tx prefix hash: 1dc84da56cb7c0400bc6cfd31d788cede3318a9e674ee5010485eae6f1b16b08
Tx public key: 4158e7fea8feed30d05be69ce02c1067eeae822795f4c3d4fce8f80b2a8748e1
Timestamp: 1725026219 Timestamp [UCT]: 2024-08-30 13:56:59 Age [y:d:h:m:s]: 00:287:10:42:30
Block: 1099216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205271 RingCT/type: yes/0
Extra: 014158e7fea8feed30d05be69ce02c1067eeae822795f4c3d4fce8f80b2a8748e1021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c610bdad12595b53aabfc0fcd37de29623d9518d7ac4330a8402dbf7c052adb5 0.600000000000 1575157 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": 1099226, "vin": [ { "gen": { "height": 1099216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c610bdad12595b53aabfc0fcd37de29623d9518d7ac4330a8402dbf7c052adb5" } } ], "extra": [ 1, 65, 88, 231, 254, 168, 254, 237, 48, 208, 91, 230, 156, 224, 44, 16, 103, 238, 174, 130, 39, 149, 244, 195, 212, 252, 232, 248, 11, 42, 135, 72, 225, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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