Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0afb6a32d837a8c0ec4012a9be0047315427c7ef55bae076618710f1a190bea5

Tx prefix hash: 495ac52686e16e8ed4493b2fe96d386b22d0530a6038e5d26ea47491ff20bc26
Tx public key: d62d2a25a23c3400831846d8cc3fd86aa3084d67938438fdd78d86b18f4cdbb4
Timestamp: 1732269003 Timestamp [UCT]: 2024-11-22 09:50:03 Age [y:d:h:m:s]: 00:001:15:42:40
Block: 1159173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1187 RingCT/type: yes/0
Extra: 01d62d2a25a23c3400831846d8cc3fd86aa3084d67938438fdd78d86b18f4cdbb4021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3595fe8dd3215c3d1a83acabfb9aae5b1e90f18a18a6e4d48a748dfe001c2f08 0.600000000000 1644806 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": 1159183, "vin": [ { "gen": { "height": 1159173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3595fe8dd3215c3d1a83acabfb9aae5b1e90f18a18a6e4d48a748dfe001c2f08" } } ], "extra": [ 1, 214, 45, 42, 37, 162, 60, 52, 0, 131, 24, 70, 216, 204, 63, 216, 106, 163, 8, 77, 103, 147, 132, 56, 253, 215, 141, 134, 177, 143, 76, 219, 180, 2, 17, 0, 0, 0, 7, 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