Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d215890c47e5352fb521ac22eec8e06439cd33ded176b945a3eff2fad7b7a35

Tx prefix hash: 369871d68be50e025cc183760321de69a86480b4fb9605c7f411e15f68edfdc8
Tx public key: c359d4b13d66aa8a249abd6466a1a6fbac39fc3ef139a9899979d02be1a4e9a4
Timestamp: 1726468680 Timestamp [UCT]: 2024-09-16 06:38:00 Age [y:d:h:m:s]: 00:179:19:24:49
Block: 1111179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128353 RingCT/type: yes/0
Extra: 01c359d4b13d66aa8a249abd6466a1a6fbac39fc3ef139a9899979d02be1a4e9a402110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c073b82e3291b1b552b2359429ad82e87a973b957c9bba6821ef296b6c5ffb9 0.600000000000 1590050 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": 1111189, "vin": [ { "gen": { "height": 1111179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c073b82e3291b1b552b2359429ad82e87a973b957c9bba6821ef296b6c5ffb9" } } ], "extra": [ 1, 195, 89, 212, 177, 61, 102, 170, 138, 36, 154, 189, 100, 102, 161, 166, 251, 172, 57, 252, 62, 241, 57, 169, 137, 153, 121, 208, 43, 225, 164, 233, 164, 2, 17, 0, 0, 0, 11, 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