Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdf62f67af4fab74b526fc263ab23b43a35d320d8ea45a090435b96bd31880f9

Tx prefix hash: 17f20cedb5c8bc777597e5041b9fd0b4b4217704d95f83d7e627643de8155db6
Tx public key: 70f6b2dfe6f90f0b3aa1ce4d2e341905d09038785e733e2a75842174834c12e6
Timestamp: 1736575602 Timestamp [UCT]: 2025-01-11 06:06:42 Age [y:d:h:m:s]: 00:071:07:46:54
Block: 1194840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50754 RingCT/type: yes/0
Extra: 0170f6b2dfe6f90f0b3aa1ce4d2e341905d09038785e733e2a75842174834c12e6021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afc3ae7cc0efdd4900f16c2835e9a873de4c269c62bd78eaf7886768242b8d4c 0.600000000000 1681417 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": 1194850, "vin": [ { "gen": { "height": 1194840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afc3ae7cc0efdd4900f16c2835e9a873de4c269c62bd78eaf7886768242b8d4c" } } ], "extra": [ 1, 112, 246, 178, 223, 230, 249, 15, 11, 58, 161, 206, 77, 46, 52, 25, 5, 208, 144, 56, 120, 94, 115, 62, 42, 117, 132, 33, 116, 131, 76, 18, 230, 2, 17, 0, 0, 0, 2, 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