Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a66ab591a0a706e2bdf9e5889d30953a62c71e997bf70c61711a1d75f4b0e02

Tx prefix hash: ac9f89339e3fe1e9f1b647ab5a112f3b93aad8486d75829c25f1e189673628b3
Tx public key: d1497ab64f7a5e172d4114b2c73e42c0b6c1c4d91d94f7bb1e88f4b079a930ed
Timestamp: 1687064976 Timestamp [UCT]: 2023-06-18 05:09:36 Age [y:d:h:m:s]: 02:143:08:35:26
Block: 784757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 622208 RingCT/type: yes/0
Extra: 01d1497ab64f7a5e172d4114b2c73e42c0b6c1c4d91d94f7bb1e88f4b079a930ed021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.540899957000 dcy

stealth address amount amount idx
00: 1aca54ad480cda1a465cfe1fa4b4d283d62c71de181000734bd650cdec743693 1.540899957000 1234658 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": 784767, "vin": [ { "gen": { "height": 784757 } } ], "vout": [ { "amount": 1540899957, "target": { "key": "1aca54ad480cda1a465cfe1fa4b4d283d62c71de181000734bd650cdec743693" } } ], "extra": [ 1, 209, 73, 122, 182, 79, 122, 94, 23, 45, 65, 20, 178, 199, 62, 66, 192, 182, 193, 196, 217, 29, 148, 247, 187, 30, 136, 244, 176, 121, 169, 48, 237, 2, 17, 0, 0, 0, 1, 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