Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea114724fe9d2febebddb55903d7044d7c79a1d7f8bd050addc292ec8d84fb54

Tx prefix hash: e95284df1b8b9b21db22fcc6a7d2a571d887272279e54e2b1e2a9939d7656ddf
Tx public key: 9b8b43e3896ddc44a9200cfb14b5abe7fd1ae990d23177bc52f72308349078c4
Timestamp: 1723783326 Timestamp [UCT]: 2024-08-16 04:42:06 Age [y:d:h:m:s]: 01:097:12:14:09
Block: 1088917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328162 RingCT/type: yes/0
Extra: 019b8b43e3896ddc44a9200cfb14b5abe7fd1ae990d23177bc52f72308349078c4021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b576133bd0af7ec2252b64609007a286c1c280bc4bafe9d785e241b972c6db64 0.600000000000 1563536 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": 1088927, "vin": [ { "gen": { "height": 1088917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b576133bd0af7ec2252b64609007a286c1c280bc4bafe9d785e241b972c6db64" } } ], "extra": [ 1, 155, 139, 67, 227, 137, 109, 220, 68, 169, 32, 12, 251, 20, 181, 171, 231, 253, 26, 233, 144, 210, 49, 119, 188, 82, 247, 35, 8, 52, 144, 120, 196, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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