Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b2133329c7268d5109b72a1fb2ae22a6ac6c2d32b8c173eaa0d4575bafa9bb4

Tx prefix hash: 717b80abfc75cffc3c72be13d2f3f2052dfbb1240c44cdd9858b0eb6572d472d
Tx public key: d298b5ff9d5ca69032a07d0181d655ff357dfaf60f054bafd58cfc2f8da33daf
Timestamp: 1720388592 Timestamp [UCT]: 2024-07-07 21:43:12 Age [y:d:h:m:s]: 00:294:00:36:01
Block: 1060781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210095 RingCT/type: yes/0
Extra: 01d298b5ff9d5ca69032a07d0181d655ff357dfaf60f054bafd58cfc2f8da33daf021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c46a83faa5fa7b5f3c6f87f8112ac5976e9dc197f7c321e368777105b122250 0.600000000000 1531266 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": 1060791, "vin": [ { "gen": { "height": 1060781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c46a83faa5fa7b5f3c6f87f8112ac5976e9dc197f7c321e368777105b122250" } } ], "extra": [ 1, 210, 152, 181, 255, 157, 92, 166, 144, 50, 160, 125, 1, 129, 214, 85, 255, 53, 125, 250, 246, 15, 5, 75, 175, 213, 140, 252, 47, 141, 163, 61, 175, 2, 17, 0, 0, 0, 3, 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