Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ed546ab5bde2ddf3b25261f192a873815d0709362b936394e3940d8d0fe4e6c

Tx prefix hash: 8cc81cc4c9057fd923babe64e42c519fc080dda02f32e99eb72d8aeee4039470
Tx public key: e2eaf61c5fa3033d592c16b63061d7a4a938c367edbe4732e7debd4554e22893
Timestamp: 1713588963 Timestamp [UCT]: 2024-04-20 04:56:03 Age [y:d:h:m:s]: 01:024:10:01:35
Block: 1004382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278441 RingCT/type: yes/0
Extra: 01e2eaf61c5fa3033d592c16b63061d7a4a938c367edbe4732e7debd4554e2289302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c565360d61e5fbf0cb55f56a7d8c0450b726ddc3c04b3658c9952741b535b79 0.600000000000 1464950 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": 1004392, "vin": [ { "gen": { "height": 1004382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c565360d61e5fbf0cb55f56a7d8c0450b726ddc3c04b3658c9952741b535b79" } } ], "extra": [ 1, 226, 234, 246, 28, 95, 163, 3, 61, 89, 44, 22, 182, 48, 97, 215, 164, 169, 56, 195, 103, 237, 190, 71, 50, 231, 222, 189, 69, 84, 226, 40, 147, 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