Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 387099173d68ddafd2f91eac646b5a11ae1d287284f4ec305ae39ff02cbf09be

Tx prefix hash: b1a48e422675568d0a89269fc3923e131a5b91deff582ad8228ce17b8ab1c2ab
Tx public key: 8638afb9b05b2e633e013ba35709cf549eaaca9e21ae19c080f539740b0a3359
Timestamp: 1685353327 Timestamp [UCT]: 2023-05-29 09:42:07 Age [y:d:h:m:s]: 02:017:22:40:29
Block: 770567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 534847 RingCT/type: yes/0
Extra: 018638afb9b05b2e633e013ba35709cf549eaaca9e21ae19c080f539740b0a335902110000000175e3f0e9000000000000000000

1 output(s) for total of 1.717085119000 dcy

stealth address amount amount idx
00: b332b4f19a4a9ceb9027a0ebcad2cb79b17e0b4ee27572a6ff9eaaf13acadf9d 1.717085119000 1219888 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": 770577, "vin": [ { "gen": { "height": 770567 } } ], "vout": [ { "amount": 1717085119, "target": { "key": "b332b4f19a4a9ceb9027a0ebcad2cb79b17e0b4ee27572a6ff9eaaf13acadf9d" } } ], "extra": [ 1, 134, 56, 175, 185, 176, 91, 46, 99, 62, 1, 59, 163, 87, 9, 207, 84, 158, 170, 202, 158, 33, 174, 25, 192, 128, 245, 57, 116, 11, 10, 51, 89, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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