Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c696b33c6e89405b509804625e8d7a1e808946fbc63f15635a5f9f11ab31a154

Tx prefix hash: 07b6b218e204380f4d6a519c470d8f5f10731f00c1df339c9fa0615d5eefa8e9
Tx public key: 72d0f746d8adb53695262cbbcdc10ee3ff6ccdab12fb59e794d0e1143f81f740
Timestamp: 1718960486 Timestamp [UCT]: 2024-06-21 09:01:26 Age [y:d:h:m:s]: 00:308:21:01:06
Block: 1048922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220747 RingCT/type: yes/0
Extra: 0172d0f746d8adb53695262cbbcdc10ee3ff6ccdab12fb59e794d0e1143f81f74002110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 384b5dd316150568d1ec672d206f311913ac282099e58e758fa6e1e660ed0521 0.600000000000 1519013 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": 1048932, "vin": [ { "gen": { "height": 1048922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "384b5dd316150568d1ec672d206f311913ac282099e58e758fa6e1e660ed0521" } } ], "extra": [ 1, 114, 208, 247, 70, 216, 173, 181, 54, 149, 38, 44, 187, 205, 193, 14, 227, 255, 108, 205, 171, 18, 251, 89, 231, 148, 208, 225, 20, 63, 129, 247, 64, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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