Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06ab318c8aa171caf7554e6ac249aa3d14c2488c4b89afa6eaaba60be5765b1d

Tx prefix hash: f614bd00826bcf18d6218ce9b5be5f5544fca7f241c1c1296f1f4d5657629336
Tx public key: 855c566cb6a556259618d754bc193df62b6b42c298655aa3ff03c9997fab8b0c
Timestamp: 1673075888 Timestamp [UCT]: 2023-01-07 07:18:08 Age [y:d:h:m:s]: 02:135:09:55:23
Block: 669386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 618515 RingCT/type: yes/0
Extra: 01855c566cb6a556259618d754bc193df62b6b42c298655aa3ff03c9997fab8b0c02110000000252542ceb000000000000000000

1 output(s) for total of 3.715748103000 dcy

stealth address amount amount idx
00: cd8473e0428f997498ecd6e64e8e354ada09f814fecc65ceecf388f82e9261be 3.715748103000 1110697 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": 669396, "vin": [ { "gen": { "height": 669386 } } ], "vout": [ { "amount": 3715748103, "target": { "key": "cd8473e0428f997498ecd6e64e8e354ada09f814fecc65ceecf388f82e9261be" } } ], "extra": [ 1, 133, 92, 86, 108, 182, 165, 86, 37, 150, 24, 215, 84, 188, 25, 61, 246, 43, 107, 66, 194, 152, 101, 90, 163, 255, 3, 201, 153, 127, 171, 139, 12, 2, 17, 0, 0, 0, 2, 82, 84, 44, 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