Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7597d28585fdb2fdbd7a04e7e26caa88040c1089c35ad51a8b5b58d72215859f

Tx prefix hash: 22d6512a0f6a32deb4c48a5058b891d2ddc8946ca0e6583ca68c6704b2209bee
Tx public key: 77a4df7949c9721d5fbaabfa91f6d8d6b20afa01a5686de8aad8299e6d46c377
Timestamp: 1710842025 Timestamp [UCT]: 2024-03-19 09:53:45 Age [y:d:h:m:s]: 01:023:07:28:46
Block: 981648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277623 RingCT/type: yes/0
Extra: 0177a4df7949c9721d5fbaabfa91f6d8d6b20afa01a5686de8aad8299e6d46c37702110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 250e217249208540e99f9c7f7d37b993539785330d37a168fa0c1b715ae9e2ad 0.600000000000 1441745 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": 981658, "vin": [ { "gen": { "height": 981648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "250e217249208540e99f9c7f7d37b993539785330d37a168fa0c1b715ae9e2ad" } } ], "extra": [ 1, 119, 164, 223, 121, 73, 201, 114, 29, 95, 186, 171, 250, 145, 246, 216, 214, 178, 10, 250, 1, 165, 104, 109, 232, 170, 216, 41, 158, 109, 70, 195, 119, 2, 17, 0, 0, 0, 8, 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