Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ba9a726827ad786d915b461cfad85e249a0dcd6a70125787c47c039d03901c2

Tx prefix hash: 83a12fb88d8ef7ceb2a3011402e214983da3371fcae9a20911fd919e2b65beb2
Tx public key: 05e87854e55b9ef198342f6a3b4bb17db5e634d752cfb702941a740302081832
Timestamp: 1706252088 Timestamp [UCT]: 2024-01-26 06:54:48 Age [y:d:h:m:s]: 01:082:11:48:27
Block: 943548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320045 RingCT/type: yes/0
Extra: 0105e87854e55b9ef198342f6a3b4bb17db5e634d752cfb702941a74030208183202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bbaf36b4caa1d4f360f08e667e0c6c27d4ecb2e6f5a79d660f344493a1b06ba 0.600000000000 1401756 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": 943558, "vin": [ { "gen": { "height": 943548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bbaf36b4caa1d4f360f08e667e0c6c27d4ecb2e6f5a79d660f344493a1b06ba" } } ], "extra": [ 1, 5, 232, 120, 84, 229, 91, 158, 241, 152, 52, 47, 106, 59, 75, 177, 125, 181, 230, 52, 215, 82, 207, 183, 2, 148, 26, 116, 3, 2, 8, 24, 50, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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