Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de2988e4dfb4dab264f1120890c1a076a6c57b78b5b26f57cc2c164c103433a2

Tx prefix hash: 4876ddf620926ea7d1f22586156e3d6c4ba1416bc332b77385bccf60f78c82ee
Tx public key: ebd70c6dd93a0e58a1d2e87eb3f22a942458bc84a38ab3a92731a628fdc3a708
Timestamp: 1734979517 Timestamp [UCT]: 2024-12-23 18:45:17 Age [y:d:h:m:s]: 00:095:03:43:47
Block: 1181645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67769 RingCT/type: yes/0
Extra: 01ebd70c6dd93a0e58a1d2e87eb3f22a942458bc84a38ab3a92731a628fdc3a7080211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c76ad0e6ad761188629688b7d073b377bfe258261d677603507a8d4fe2590068 0.600000000000 1668070 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": 1181655, "vin": [ { "gen": { "height": 1181645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c76ad0e6ad761188629688b7d073b377bfe258261d677603507a8d4fe2590068" } } ], "extra": [ 1, 235, 215, 12, 109, 217, 58, 14, 88, 161, 210, 232, 126, 179, 242, 42, 148, 36, 88, 188, 132, 163, 138, 179, 169, 39, 49, 166, 40, 253, 195, 167, 8, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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