Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3b3d06d8115be40a126a11a1267bb824c9cb2762b7645b6d7bbc0d974ab3033

Tx prefix hash: ab3736ff3612d67bcae467dd66dfc23944ac7e82475ae5c4cb71244389f26460
Tx public key: 5d7eb6a76cbafa358ac4a3c401dcce28544c09017bb47b51c641eaaa03acf6c9
Timestamp: 1677951443 Timestamp [UCT]: 2023-03-04 17:37:23 Age [y:d:h:m:s]: 02:032:17:40:56
Block: 709837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544965 RingCT/type: yes/0
Extra: 015d7eb6a76cbafa358ac4a3c401dcce28544c09017bb47b51c641eaaa03acf6c90211000000015029cbac000000000000000000

1 output(s) for total of 2.729073614000 dcy

stealth address amount amount idx
00: 62d1eadb6fa12ea9d7748eb816aa3347ddb2052c0c927a01f0f763253481a3a1 2.729073614000 1153856 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": 709847, "vin": [ { "gen": { "height": 709837 } } ], "vout": [ { "amount": 2729073614, "target": { "key": "62d1eadb6fa12ea9d7748eb816aa3347ddb2052c0c927a01f0f763253481a3a1" } } ], "extra": [ 1, 93, 126, 182, 167, 108, 186, 250, 53, 138, 196, 163, 196, 1, 220, 206, 40, 84, 76, 9, 1, 123, 180, 123, 81, 198, 65, 234, 170, 3, 172, 246, 201, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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