Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79f06a80c96c4f172495e805926b08a38bf6663cc1dc17beb2ad4e05f11bac26

Tx prefix hash: 08655b0e76f3db4802d11bcd64b5818542c9f3bd48ea1c9db1945acb3ade5aee
Tx public key: d91203d1671c04b893ee3d6d6fcdd3a74d3bbe0a940137239f16d18dba891c60
Timestamp: 1731898708 Timestamp [UCT]: 2024-11-18 02:58:28 Age [y:d:h:m:s]: 00:125:03:38:14
Block: 1156108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89260 RingCT/type: yes/0
Extra: 01d91203d1671c04b893ee3d6d6fcdd3a74d3bbe0a940137239f16d18dba891c60021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 742fb25dd05d4f7a13fb20411e952bfe07b925b18f52baa2a1e5e2a62dfae3af 0.600000000000 1641731 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": 1156118, "vin": [ { "gen": { "height": 1156108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "742fb25dd05d4f7a13fb20411e952bfe07b925b18f52baa2a1e5e2a62dfae3af" } } ], "extra": [ 1, 217, 18, 3, 209, 103, 28, 4, 184, 147, 238, 61, 109, 111, 205, 211, 167, 77, 59, 190, 10, 148, 1, 55, 35, 159, 22, 209, 141, 186, 137, 28, 96, 2, 17, 0, 0, 0, 4, 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