Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da6cc260798d58fe51d3296f3ed69bc5385793dc94195248ddb17d98dc3fc14a

Tx prefix hash: cd34ba6be8329660d776d27376c804d7c8378db3f422ccb9f8a8c780d63a3778
Tx public key: 1959838779633409ea9f6b0d7327411e963ca9dcec561b8d3ee32977581e5fd1
Timestamp: 1695817976 Timestamp [UCT]: 2023-09-27 12:32:56 Age [y:d:h:m:s]: 01:196:16:22:37
Block: 857276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401636 RingCT/type: yes/0
Extra: 011959838779633409ea9f6b0d7327411e963ca9dcec561b8d3ee32977581e5fd102110000000633af99f4000000000000000000

1 output(s) for total of 0.886112342000 dcy

stealth address amount amount idx
00: f018ca5f4b3e6a3f2a1146b6718e9eede11f4c942bd0d026094963a7cafaac28 0.886112342000 1311390 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": 857286, "vin": [ { "gen": { "height": 857276 } } ], "vout": [ { "amount": 886112342, "target": { "key": "f018ca5f4b3e6a3f2a1146b6718e9eede11f4c942bd0d026094963a7cafaac28" } } ], "extra": [ 1, 25, 89, 131, 135, 121, 99, 52, 9, 234, 159, 107, 13, 115, 39, 65, 30, 150, 60, 169, 220, 236, 86, 27, 141, 62, 227, 41, 119, 88, 30, 95, 209, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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