Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ca9ad00c8de262a43e6598190c856f2e7974bb6c455b59edb33467b580e14b0

Tx prefix hash: a2bb9742b65a1e637fe5cfc13b33efcfc3e9e550d308e533fc8fcd3eacac3616
Tx public key: 7b0ab3c431983cd15b747ca2e8c37941bd8369066fb29c647837903b1f24b6d7
Timestamp: 1733249755 Timestamp [UCT]: 2024-12-03 18:15:55 Age [y:d:h:m:s]: 00:024:16:25:15
Block: 1167302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17655 RingCT/type: yes/0
Extra: 017b0ab3c431983cd15b747ca2e8c37941bd8369066fb29c647837903b1f24b6d7021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5be4341559a0d2e10025d36c081fb896ac52cab4c6d80c5385d2b4f40861ef2 0.600000000000 1652997 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": 1167312, "vin": [ { "gen": { "height": 1167302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5be4341559a0d2e10025d36c081fb896ac52cab4c6d80c5385d2b4f40861ef2" } } ], "extra": [ 1, 123, 10, 179, 196, 49, 152, 60, 209, 91, 116, 124, 162, 232, 195, 121, 65, 189, 131, 105, 6, 111, 178, 156, 100, 120, 55, 144, 59, 31, 36, 182, 215, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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