Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45983ac2a65d350a8d7fe2fb7e04192280043e1cee10288367a063b7028def88

Tx prefix hash: bb657c128a9f30d62461e81288c1081940d9ae4e6d4a7be92bac0d1d427906ce
Tx public key: 2a3e85d904f3f557cc308c11e671c5cf9ae3651e356b15d1e7c828aa21038602
Timestamp: 1728545044 Timestamp [UCT]: 2024-10-10 07:24:04 Age [y:d:h:m:s]: 00:161:11:54:55
Block: 1128395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115224 RingCT/type: yes/0
Extra: 012a3e85d904f3f557cc308c11e671c5cf9ae3651e356b15d1e7c828aa2103860202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce2e2ac56e72601807c615e49f88b256914fbb38e39327b9b494ec901176fb6d 0.600000000000 1611212 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": 1128405, "vin": [ { "gen": { "height": 1128395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce2e2ac56e72601807c615e49f88b256914fbb38e39327b9b494ec901176fb6d" } } ], "extra": [ 1, 42, 62, 133, 217, 4, 243, 245, 87, 204, 48, 140, 17, 230, 113, 197, 207, 154, 227, 101, 30, 53, 107, 21, 209, 231, 200, 40, 170, 33, 3, 134, 2, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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