Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4b3c7001f6ccafb287c72c5f83d26be1570631e67c30033ab2e7f57d478173f

Tx prefix hash: f198f3ed578f31e1d7da1efd94aee57cd5046d0ac651ca6d1f0a8b507b0f9f55
Tx public key: ba4bc15ed6efe66a0829489e725c543310ad2ac97016ffee19fae5576f1510a3
Timestamp: 1681384311 Timestamp [UCT]: 2023-04-13 11:11:51 Age [y:d:h:m:s]: 02:011:19:52:20
Block: 737637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530633 RingCT/type: yes/0
Extra: 01ba4bc15ed6efe66a0829489e725c543310ad2ac97016ffee19fae5576f1510a3021100000002e6d27f9c000000000000000000

1 output(s) for total of 2.207509761000 dcy

stealth address amount amount idx
00: b1c4ec8740ddc81ed05dca9d047d9bc0a9f90b1f4fa794631d5ff3af486c88d7 2.207509761000 1184226 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": 737647, "vin": [ { "gen": { "height": 737637 } } ], "vout": [ { "amount": 2207509761, "target": { "key": "b1c4ec8740ddc81ed05dca9d047d9bc0a9f90b1f4fa794631d5ff3af486c88d7" } } ], "extra": [ 1, 186, 75, 193, 94, 214, 239, 230, 106, 8, 41, 72, 158, 114, 92, 84, 51, 16, 173, 42, 201, 112, 22, 255, 238, 25, 250, 229, 87, 111, 21, 16, 163, 2, 17, 0, 0, 0, 2, 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