Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a30764e22b9df9dbc77efa0e824ab0b91d9c75184bde4c09738ecfa972b882e

Tx prefix hash: 34e5fe7e087ed01ee7dffe1410590f8792afe55e3fc89983edf06bc02538b2fc
Tx public key: ed108f8ce146b73c01a55491cbe6720554cf00383b3c8a32eb041fe16c252c8d
Timestamp: 1736129096 Timestamp [UCT]: 2025-01-06 02:04:56 Age [y:d:h:m:s]: 00:302:18:07:10
Block: 1191145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213870 RingCT/type: yes/0
Extra: 01ed108f8ce146b73c01a55491cbe6720554cf00383b3c8a32eb041fe16c252c8d02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfba6bf1c7e0a6c1a0c625e9b24501f127f8517f770a06e3cd92df267ce9d98d 0.600000000000 1677668 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": 1191155, "vin": [ { "gen": { "height": 1191145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfba6bf1c7e0a6c1a0c625e9b24501f127f8517f770a06e3cd92df267ce9d98d" } } ], "extra": [ 1, 237, 16, 143, 140, 225, 70, 183, 60, 1, 165, 84, 145, 203, 230, 114, 5, 84, 207, 0, 56, 59, 60, 138, 50, 235, 4, 31, 225, 108, 37, 44, 141, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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