Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a1138d5c566b28f529a3c63aa2a8b5372beaa2ae5b79ab0af2f996c796816b4

Tx prefix hash: bab3539f9862f6bdbd391e579051dd029ecfcd4f22a9c61cc30a330536fea2d3
Tx public key: 8320093ffd6330177e79caff5e064dee9766c7ad321793a4454d636b97003018
Timestamp: 1697298731 Timestamp [UCT]: 2023-10-14 15:52:11 Age [y:d:h:m:s]: 01:162:05:19:04
Block: 869548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376963 RingCT/type: yes/0
Extra: 018320093ffd6330177e79caff5e064dee9766c7ad321793a4454d636b97003018021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.806912675000 dcy

stealth address amount amount idx
00: aa7445e52abe62010d9f98c7c7a8657a6d4ddd91a82745e5c3ad1f65441eb357 0.806912675000 1324397 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": 869558, "vin": [ { "gen": { "height": 869548 } } ], "vout": [ { "amount": 806912675, "target": { "key": "aa7445e52abe62010d9f98c7c7a8657a6d4ddd91a82745e5c3ad1f65441eb357" } } ], "extra": [ 1, 131, 32, 9, 63, 253, 99, 48, 23, 126, 121, 202, 255, 94, 6, 77, 238, 151, 102, 199, 173, 50, 23, 147, 164, 69, 77, 99, 107, 151, 0, 48, 24, 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