Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5356f9f058d9c5fca3cb433a8fe201bc28f5a50f23e72091ae6e377751013c85

Tx prefix hash: af89964ca4ec394fc2895941c637d2951e48cc1d661365ca7fa0707b46ce9f19
Tx public key: 17e9bb89d488721ebef95427c0e3a81f71ecda5b8b3f220b0a3ce8ac7c695514
Timestamp: 1731986568 Timestamp [UCT]: 2024-11-19 03:22:48 Age [y:d:h:m:s]: 00:150:10:40:30
Block: 1156843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107344 RingCT/type: yes/0
Extra: 0117e9bb89d488721ebef95427c0e3a81f71ecda5b8b3f220b0a3ce8ac7c695514021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a222bfa8c1dd1164f96a8fd8375f40be434d2d0c9f63d5f293ebdd7e08287bb 0.600000000000 1642466 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": 1156853, "vin": [ { "gen": { "height": 1156843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a222bfa8c1dd1164f96a8fd8375f40be434d2d0c9f63d5f293ebdd7e08287bb" } } ], "extra": [ 1, 23, 233, 187, 137, 212, 136, 114, 30, 190, 249, 84, 39, 192, 227, 168, 31, 113, 236, 218, 91, 139, 63, 34, 11, 10, 60, 232, 172, 124, 105, 85, 20, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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