Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f33b3e4eef93236dad6b1ad11d11789f8b1799944ac2a0feb98ffbb40725459e

Tx prefix hash: 4fa1c0fa1d1dfe9e4d6533c95f9291b5fc3a9afe897602abe76adcaa170dc641
Tx public key: 869df2ed675f2e0430d176fd36592d335783d0f0e934af8c1507e11e2c3b4c67
Timestamp: 1729751217 Timestamp [UCT]: 2024-10-24 06:26:57 Age [y:d:h:m:s]: 00:187:09:50:48
Block: 1138370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133759 RingCT/type: yes/0
Extra: 01869df2ed675f2e0430d176fd36592d335783d0f0e934af8c1507e11e2c3b4c67021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bb4e4c3d5da9c2b9daec5fd840c1bf5e1aa9a7cb2d9f0328ea821a538a22140 0.600000000000 1622017 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": 1138380, "vin": [ { "gen": { "height": 1138370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bb4e4c3d5da9c2b9daec5fd840c1bf5e1aa9a7cb2d9f0328ea821a538a22140" } } ], "extra": [ 1, 134, 157, 242, 237, 103, 95, 46, 4, 48, 209, 118, 253, 54, 89, 45, 51, 87, 131, 208, 240, 233, 52, 175, 140, 21, 7, 225, 30, 44, 59, 76, 103, 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