Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ce16d78a81cf46f1d1c1106c1270f60c60751db1aa28fe5907776e21ae3cf4c

Tx prefix hash: 859b098308196cf05bdcd66ab8b171d0ca92b511a63165d6004f53332d5086df
Tx public key: 608d61f415917b6d875235950d7f32bec49c03e96acfb0a48b4bbcc1dfac13ea
Timestamp: 1723290733 Timestamp [UCT]: 2024-08-10 11:52:13 Age [y:d:h:m:s]: 00:227:18:09:30
Block: 1084846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162634 RingCT/type: yes/0
Extra: 01608d61f415917b6d875235950d7f32bec49c03e96acfb0a48b4bbcc1dfac13ea02110000000991e13c04000000000000000000

1 output(s) for total of 0.615590000000 dcy

stealth address amount amount idx
00: e59712a3906051163bb0b06b3ad3e902e3c316101e98c1e26e99703a634af47b 0.615590000000 1559265 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": 1084856, "vin": [ { "gen": { "height": 1084846 } } ], "vout": [ { "amount": 615590000, "target": { "key": "e59712a3906051163bb0b06b3ad3e902e3c316101e98c1e26e99703a634af47b" } } ], "extra": [ 1, 96, 141, 97, 244, 21, 145, 123, 109, 135, 82, 53, 149, 13, 127, 50, 190, 196, 156, 3, 233, 106, 207, 176, 164, 139, 75, 188, 193, 223, 172, 19, 234, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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