Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d9d933745c42810955ee7c7e77eae0cd70926d051db16d3b07e43eaf70bb80a

Tx prefix hash: 761c3ae5313cb2d14dbff0671140d5eb44879ce8310d098a47648c2b0c72138c
Tx public key: c66e7b056ec8c6f19f7602c3a273bf4261a03bc0abccb782122bc09afab91b77
Timestamp: 1583753706 Timestamp [UCT]: 2020-03-09 11:35:06 Age [y:d:h:m:s]: 05:063:02:25:33
Block: 79470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200445 RingCT/type: yes/0
Extra: 01c66e7b056ec8c6f19f7602c3a273bf4261a03bc0abccb782122bc09afab91b770211000000046d997e00000000000000000000

1 output(s) for total of 334.721563262000 dcy

stealth address amount amount idx
00: 3fbf29ee67b239f825217b9b0bb9fb2ac346c80b6ebf65d9bcb3a7c1fdc4a52f 334.721563262000 145324 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": 79480, "vin": [ { "gen": { "height": 79470 } } ], "vout": [ { "amount": 334721563262, "target": { "key": "3fbf29ee67b239f825217b9b0bb9fb2ac346c80b6ebf65d9bcb3a7c1fdc4a52f" } } ], "extra": [ 1, 198, 110, 123, 5, 110, 200, 198, 241, 159, 118, 2, 195, 162, 115, 191, 66, 97, 160, 59, 192, 171, 204, 183, 130, 18, 43, 192, 154, 250, 185, 27, 119, 2, 17, 0, 0, 0, 4, 109, 153, 126, 0, 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