Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de7ef3aa563780381e84fdf92db4ff9e645b52da99d444ff3714bd4dbfaf52b9

Tx prefix hash: 0d4e75f51c5d9779c42d22c503a4232a43e102cc04db69664c1f9e8906a17c02
Tx public key: 86aa5c3902d4e9e41ea5582370364d7c59fed279255f32dc1c0de456327fdd1f
Timestamp: 1738069542 Timestamp [UCT]: 2025-01-28 13:05:42 Age [y:d:h:m:s]: 00:044:23:30:22
Block: 1206949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32183 RingCT/type: yes/0
Extra: 0186aa5c3902d4e9e41ea5582370364d7c59fed279255f32dc1c0de456327fdd1f021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c09d45d72fded4eca9eebecb3f33798395e0f56e6fa24bad9667fd65bc4258a 0.600000000000 1693668 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": 1206959, "vin": [ { "gen": { "height": 1206949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c09d45d72fded4eca9eebecb3f33798395e0f56e6fa24bad9667fd65bc4258a" } } ], "extra": [ 1, 134, 170, 92, 57, 2, 212, 233, 228, 30, 165, 88, 35, 112, 54, 77, 124, 89, 254, 210, 121, 37, 95, 50, 220, 28, 13, 228, 86, 50, 127, 221, 31, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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