Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 689c97eb827003867f5417bd21e88f9e0aac502c152c64f69f49e6c34fce9328

Tx prefix hash: 0aac6997cd597b95ac01339cd9c47ea4a1761930510e437c3cba87f36f39e25a
Tx public key: e1179daa5ba16b46f2ce9c1f33b86c8a4800ea35d82d932d2d1200fbcdff43ca
Timestamp: 1707529133 Timestamp [UCT]: 2024-02-10 01:38:53 Age [y:d:h:m:s]: 00:338:07:53:40
Block: 954158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242217 RingCT/type: yes/0
Extra: 01e1179daa5ba16b46f2ce9c1f33b86c8a4800ea35d82d932d2d1200fbcdff43ca02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cc2ba42a2af55cc5718c3ee153d5dddbc0f492678507d1a6a39b42d071a72c1 0.600000000000 1413434 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": 954168, "vin": [ { "gen": { "height": 954158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cc2ba42a2af55cc5718c3ee153d5dddbc0f492678507d1a6a39b42d071a72c1" } } ], "extra": [ 1, 225, 23, 157, 170, 91, 161, 107, 70, 242, 206, 156, 31, 51, 184, 108, 138, 72, 0, 234, 53, 216, 45, 147, 45, 45, 18, 0, 251, 205, 255, 67, 202, 2, 17, 0, 0, 0, 5, 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