Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bfd86c366b2ce0e363452fc89e5b7fc97630cb8febc4a5858210b2d2625d631

Tx prefix hash: 03975baae08940c2dce7c415b45f1ac26f86178cc203629fca097280f73f7105
Tx public key: ae0645fb38f2cebd5b572b3c1b178f75d3a1cfc21171acdd4d4bcadbdeaeef89
Timestamp: 1737779680 Timestamp [UCT]: 2025-01-25 04:34:40 Age [y:d:h:m:s]: 00:144:02:26:32
Block: 1204764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102731 RingCT/type: yes/0
Extra: 01ae0645fb38f2cebd5b572b3c1b178f75d3a1cfc21171acdd4d4bcadbdeaeef89021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 094612eca1193a779737ee203cc79f0bbecd33f9eb5e0ecc5d7be60fc6c341da 0.600000000000 1691457 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": 1204774, "vin": [ { "gen": { "height": 1204764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "094612eca1193a779737ee203cc79f0bbecd33f9eb5e0ecc5d7be60fc6c341da" } } ], "extra": [ 1, 174, 6, 69, 251, 56, 242, 206, 189, 91, 87, 43, 60, 27, 23, 143, 117, 211, 161, 207, 194, 17, 113, 172, 221, 77, 75, 202, 219, 222, 174, 239, 137, 2, 17, 0, 0, 0, 4, 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