Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72cccbe09417d8367e819fbc83eb9a9ded98a7244b7fd2f782ac78ba2221e235

Tx prefix hash: 93ca4ace522aac2d6ecff241fd062f1970b4856e46373036f51bd62601368062
Tx public key: 2e2865c4a42593971e3e0dd606059d27648c48c5ac5b06c259a9a5dfdc8b57c8
Timestamp: 1718076082 Timestamp [UCT]: 2024-06-11 03:21:22 Age [y:d:h:m:s]: 01:004:15:25:02
Block: 1041617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264104 RingCT/type: yes/0
Extra: 012e2865c4a42593971e3e0dd606059d27648c48c5ac5b06c259a9a5dfdc8b57c802110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e58a179f1251ad3c398a0267977419bb3402138ea3c83acbef547450e74476c 0.600000000000 1510334 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": 1041627, "vin": [ { "gen": { "height": 1041617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e58a179f1251ad3c398a0267977419bb3402138ea3c83acbef547450e74476c" } } ], "extra": [ 1, 46, 40, 101, 196, 164, 37, 147, 151, 30, 62, 13, 214, 6, 5, 157, 39, 100, 140, 72, 197, 172, 91, 6, 194, 89, 169, 165, 223, 220, 139, 87, 200, 2, 17, 0, 0, 0, 4, 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