Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29bc83d594dcfa439b83feb6b19cd0a328a7eb2d3f1f4d7f18144f97239232da

Tx prefix hash: 4b433a8e64eab41fa0440b93731820ddd4aeca6b22163ecc207431b319d2c02a
Tx public key: 0ca967548d7c7ffc4c00f3ecb5ad412b7fbe9c2c96880e647dc9bc7794191d59
Timestamp: 1582930502 Timestamp [UCT]: 2020-02-28 22:55:02 Age [y:d:h:m:s]: 05:094:03:07:38
Block: 73665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1221659 RingCT/type: yes/0
Extra: 010ca967548d7c7ffc4c00f3ecb5ad412b7fbe9c2c96880e647dc9bc7794191d5902110000000a724f989b000000000000000000

1 output(s) for total of 349.879159391000 dcy

stealth address amount amount idx
00: 8e31cd8df1a1c0c819a15d962b5c8b2a3293355e799b7daec22d050b5efd0e15 349.879159391000 135936 of 0

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": 73675, "vin": [ { "gen": { "height": 73665 } } ], "vout": [ { "amount": 349879159391, "target": { "key": "8e31cd8df1a1c0c819a15d962b5c8b2a3293355e799b7daec22d050b5efd0e15" } } ], "extra": [ 1, 12, 169, 103, 84, 141, 124, 127, 252, 76, 0, 243, 236, 181, 173, 65, 43, 127, 190, 156, 44, 150, 136, 14, 100, 125, 201, 188, 119, 148, 25, 29, 89, 2, 17, 0, 0, 0, 10, 114, 79, 152, 155, 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