Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a2054833b60572388c66f9f97132840a3cfb75bd1b7137f75b133ba5310e17c

Tx prefix hash: f22fab071d76df9c099d1421f3347724118e84597ec509e4719c450f885580c8
Tx public key: c169c42a744278eb419dfe25a9eb141b3b281991e3df1f434c743efadefebc9e
Timestamp: 1698327095 Timestamp [UCT]: 2023-10-26 13:31:35 Age [y:d:h:m:s]: 01:095:10:31:48
Block: 878103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329168 RingCT/type: yes/0
Extra: 01c169c42a744278eb419dfe25a9eb141b3b281991e3df1f434c743efadefebc9e0211000000054b8f5122000000000000000000

1 output(s) for total of 0.755927698000 dcy

stealth address amount amount idx
00: 4f51a109968fc84b245d9f7f77c8a1a2744dbfb6d4caca81c8d4e3f38ad15085 0.755927698000 1333517 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": 878113, "vin": [ { "gen": { "height": 878103 } } ], "vout": [ { "amount": 755927698, "target": { "key": "4f51a109968fc84b245d9f7f77c8a1a2744dbfb6d4caca81c8d4e3f38ad15085" } } ], "extra": [ 1, 193, 105, 196, 42, 116, 66, 120, 235, 65, 157, 254, 37, 169, 235, 20, 27, 59, 40, 25, 145, 227, 223, 31, 67, 76, 116, 62, 250, 222, 254, 188, 158, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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