Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2d3cbe7c20e657bfc66de42944ead358073a9ec144706a18f92048475c977b5

Tx prefix hash: 0eb389a9165c4df336887192e3adbc6612834a6a4ce34277ab2c77494799f0b7
Tx public key: 63b0db61e77736379c53081bc1318a2e55c2f2a4785cd7845f87aeddc6805a56
Timestamp: 1725623296 Timestamp [UCT]: 2024-09-06 11:48:16 Age [y:d:h:m:s]: 00:047:10:37:37
Block: 1104181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33951 RingCT/type: yes/0
Extra: 0163b0db61e77736379c53081bc1318a2e55c2f2a4785cd7845f87aeddc6805a5602110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d1168a06f89d0b1a9d19fff0c2b7d4da931c812498c16b5e1d50b841347d4df 0.600000000000 1581260 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": 1104191, "vin": [ { "gen": { "height": 1104181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d1168a06f89d0b1a9d19fff0c2b7d4da931c812498c16b5e1d50b841347d4df" } } ], "extra": [ 1, 99, 176, 219, 97, 231, 119, 54, 55, 156, 83, 8, 27, 193, 49, 138, 46, 85, 194, 242, 164, 120, 92, 215, 132, 95, 135, 174, 221, 198, 128, 90, 86, 2, 17, 0, 0, 0, 8, 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