Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f510bc29d08fc32e9aab5f7b1bebde8b4d58d74a277f9b54014cea35d920f251

Tx prefix hash: 64b1f75348e5d7c84834c6661de6297f22d3fa88b372010a2321622c7cf46d3a
Tx public key: d2c64df80b339e814ee9a849dd433f9c6c5518aa2a4d0bd274ed80665a177203
Timestamp: 1732957084 Timestamp [UCT]: 2024-11-30 08:58:04 Age [y:d:h:m:s]: 00:119:10:38:37
Block: 1164883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85164 RingCT/type: yes/0
Extra: 01d2c64df80b339e814ee9a849dd433f9c6c5518aa2a4d0bd274ed80665a177203021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84d8cb004005afc7704ad0a71fb6ffeb20a83100666aa815fbdf2bd5bd254313 0.600000000000 1650558 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": 1164893, "vin": [ { "gen": { "height": 1164883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84d8cb004005afc7704ad0a71fb6ffeb20a83100666aa815fbdf2bd5bd254313" } } ], "extra": [ 1, 210, 198, 77, 248, 11, 51, 158, 129, 78, 233, 168, 73, 221, 67, 63, 156, 108, 85, 24, 170, 42, 77, 11, 210, 116, 237, 128, 102, 90, 23, 114, 3, 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