Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bce7be46585fc6502d10b9ad1f9017cbd1ba0d10fbfaca5e64ebe39ff4b9efd

Tx prefix hash: 38a8444c89c16c9dfdd58d036878a2da8ab52e5b630d8f3ecfdf638f43c1366c
Tx public key: a54ceb3349f63cde702e78246e17d618f93397d90e97cf133d20c8f13a7c36b2
Timestamp: 1708805536 Timestamp [UCT]: 2024-02-24 20:12:16 Age [y:d:h:m:s]: 01:263:04:10:31
Block: 964748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446837 RingCT/type: yes/0
Extra: 01a54ceb3349f63cde702e78246e17d618f93397d90e97cf133d20c8f13a7c36b2021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0f2910b1af05421db602c05630eb43cfccc803bb352b880971dbe7e38e79818 0.600000000000 1424491 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": 964758, "vin": [ { "gen": { "height": 964748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0f2910b1af05421db602c05630eb43cfccc803bb352b880971dbe7e38e79818" } } ], "extra": [ 1, 165, 76, 235, 51, 73, 246, 60, 222, 112, 46, 120, 36, 110, 23, 214, 24, 249, 51, 151, 217, 14, 151, 207, 19, 61, 32, 200, 241, 58, 124, 54, 178, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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