Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fc69cf23b7929ee2e5025cb1465b010083cfab9e26959cecd067127a741f4af

Tx prefix hash: 385865f9d5e3ef4ad63c09f34ba3f1d9e71330b598aa2faadf1e4d66777805c0
Tx public key: 57c7900c425965ac71ccc36cbb0a30ea3e4cd36df332c830ca8c37f158d5cb61
Timestamp: 1672803629 Timestamp [UCT]: 2023-01-04 03:40:29 Age [y:d:h:m:s]: 02:097:04:53:47
Block: 667149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 591150 RingCT/type: yes/0
Extra: 0157c7900c425965ac71ccc36cbb0a30ea3e4cd36df332c830ca8c37f158d5cb61021100000003faf35c9c000000000000000000

1 output(s) for total of 3.779709112000 dcy

stealth address amount amount idx
00: c76de67abcfbca9525f704737a00136ace3bfc895f4d123a1237ece15915b032 3.779709112000 1108314 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": 667159, "vin": [ { "gen": { "height": 667149 } } ], "vout": [ { "amount": 3779709112, "target": { "key": "c76de67abcfbca9525f704737a00136ace3bfc895f4d123a1237ece15915b032" } } ], "extra": [ 1, 87, 199, 144, 12, 66, 89, 101, 172, 113, 204, 195, 108, 187, 10, 48, 234, 62, 76, 211, 109, 243, 50, 200, 48, 202, 140, 55, 241, 88, 213, 203, 97, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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