Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3deaab4fe0529085e103793e92fe18dd9d4717880bfbd5b7a5255a0a399ba3bb

Tx prefix hash: 07d3175107cb065c15de39f08a86e215dd1371cf6e5c8d51160d2df56c43a886
Tx public key: 7c2327219ddd7a4f9f8b2266f8cb9405ba227a5c293e97ae1f06f549b62a66b4
Timestamp: 1699092929 Timestamp [UCT]: 2023-11-04 10:15:29 Age [y:d:h:m:s]: 01:076:15:58:00
Block: 884433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315976 RingCT/type: yes/0
Extra: 017c2327219ddd7a4f9f8b2266f8cb9405ba227a5c293e97ae1f06f549b62a66b402110000000233af99f4000000000000000000

1 output(s) for total of 0.720288252000 dcy

stealth address amount amount idx
00: 357918c3bddc02363a8ed17b4d0cab191b1a81720c4c88892f4f499d1deb1d00 0.720288252000 1340172 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": 884443, "vin": [ { "gen": { "height": 884433 } } ], "vout": [ { "amount": 720288252, "target": { "key": "357918c3bddc02363a8ed17b4d0cab191b1a81720c4c88892f4f499d1deb1d00" } } ], "extra": [ 1, 124, 35, 39, 33, 157, 221, 122, 79, 159, 139, 34, 102, 248, 203, 148, 5, 186, 34, 122, 92, 41, 62, 151, 174, 31, 6, 245, 73, 182, 42, 102, 180, 2, 17, 0, 0, 0, 2, 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