Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b7eaaa6dbe4b65c43da045158990a0e9c51608ff9a8956e00ad5013a81a019f

Tx prefix hash: 2ab64b2761caee13640c4ba967a65e89d64c47ea61ecdae2f4914277c1e3142e
Tx public key: 6a973aaa11b4df7e5cb033f3d19386054210c3285d9eac7bb9b9f322548a6078
Timestamp: 1702754144 Timestamp [UCT]: 2023-12-16 19:15:44 Age [y:d:h:m:s]: 01:152:16:47:50
Block: 914577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370297 RingCT/type: yes/0
Extra: 016a973aaa11b4df7e5cb033f3d19386054210c3285d9eac7bb9b9f322548a6078021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.617870000000 dcy

stealth address amount amount idx
00: 07509773ee9c003e557553f7fc3259f081716a3c5709e9511458d49a45df4f0a 0.617870000000 1371919 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": 914587, "vin": [ { "gen": { "height": 914577 } } ], "vout": [ { "amount": 617870000, "target": { "key": "07509773ee9c003e557553f7fc3259f081716a3c5709e9511458d49a45df4f0a" } } ], "extra": [ 1, 106, 151, 58, 170, 17, 180, 223, 126, 92, 176, 51, 243, 209, 147, 134, 5, 66, 16, 195, 40, 93, 158, 172, 123, 185, 185, 243, 34, 84, 138, 96, 120, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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