Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51227b0cc1f88a76c71236091e94829dc68da7dad4f85f07d7e569fd3950f2e5

Tx prefix hash: b01d9181c53a7f86fa6845dbdb79a5095224060460359020ea3c3c927ea67f1d
Tx public key: cfe954faec67a2ff7c58af10ff02dcc57745b401d25727d5ba9069654d0e4aaf
Timestamp: 1704304516 Timestamp [UCT]: 2024-01-03 17:55:16 Age [y:d:h:m:s]: 01:307:00:42:09
Block: 927428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478244 RingCT/type: yes/0
Extra: 01cfe954faec67a2ff7c58af10ff02dcc57745b401d25727d5ba9069654d0e4aaf021100000001bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd79c247a44e8d509fa48a9443e6cad4e258f64009a51d303b8234b0758d3578 0.600000000000 1385264 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": 927438, "vin": [ { "gen": { "height": 927428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd79c247a44e8d509fa48a9443e6cad4e258f64009a51d303b8234b0758d3578" } } ], "extra": [ 1, 207, 233, 84, 250, 236, 103, 162, 255, 124, 88, 175, 16, 255, 2, 220, 197, 119, 69, 180, 1, 210, 87, 39, 213, 186, 144, 105, 101, 77, 14, 74, 175, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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