Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a37f28de89125c7f5ee9712cc475d879d5af44a1e986d315c9148d13bda3f92

Tx prefix hash: ae9ef431aee097c4f9ca1a8d3b2d6cfe729b4339d67b07264ab5bf6543db723a
Tx public key: bb20dbdc2d99b0963c57a86ef97f2a7a8fbcb229d165a7f0f902a0b9ef09f771
Timestamp: 1720668877 Timestamp [UCT]: 2024-07-11 03:34:37 Age [y:d:h:m:s]: 00:317:06:19:27
Block: 1063105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226717 RingCT/type: yes/0
Extra: 01bb20dbdc2d99b0963c57a86ef97f2a7a8fbcb229d165a7f0f902a0b9ef09f771021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0625430b22d7fc32bc070909c0e8bdb8c4eaf76477847ce3dc1a22c492b22e2 0.600000000000 1533618 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": 1063115, "vin": [ { "gen": { "height": 1063105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0625430b22d7fc32bc070909c0e8bdb8c4eaf76477847ce3dc1a22c492b22e2" } } ], "extra": [ 1, 187, 32, 219, 220, 45, 153, 176, 150, 60, 87, 168, 110, 249, 127, 42, 122, 143, 188, 178, 41, 209, 101, 167, 240, 249, 2, 160, 185, 239, 9, 247, 113, 2, 17, 0, 0, 0, 5, 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