Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 076c807da5b25d895a4b789aec78a3726282d7cc29d0311172b7a6fef950d993

Tx prefix hash: 5e0cd0abe6825ac0b6cbe9885fb2f1e11edc0c100088a688c0b8a5c8defaf8b7
Tx public key: 364138a8a54faa51d1790a5ecd2bfaf1bdc189607e4e624df95dc4f3cae9e1f8
Timestamp: 1697268942 Timestamp [UCT]: 2023-10-14 07:35:42 Age [y:d:h:m:s]: 01:033:04:14:10
Block: 869306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284917 RingCT/type: yes/0
Extra: 01364138a8a54faa51d1790a5ecd2bfaf1bdc189607e4e624df95dc4f3cae9e1f802110000000375e3f0e9000000000000000000

1 output(s) for total of 0.808403871000 dcy

stealth address amount amount idx
00: be5675f4efd9618f3fdad33c0944e31e42c86d032052c8379d66ceef36d2db3b 0.808403871000 1324147 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": 869316, "vin": [ { "gen": { "height": 869306 } } ], "vout": [ { "amount": 808403871, "target": { "key": "be5675f4efd9618f3fdad33c0944e31e42c86d032052c8379d66ceef36d2db3b" } } ], "extra": [ 1, 54, 65, 56, 168, 165, 79, 170, 81, 209, 121, 10, 94, 205, 43, 250, 241, 189, 193, 137, 96, 126, 78, 98, 77, 249, 93, 196, 243, 202, 233, 225, 248, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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